Hi Manfred -
Just a very fundamental suggestion. In your Java source code, make sure that you are cleaning up (ie, setting to null) all global objects. For example, set all Strings, HashMaps, Vectors, Connections, etc, to null. In theory, this should finalize any objects that may be hanging around in memory. If you have any instances of custom defined objects, clean them up as well (you can do this in a finalize method if necessary). When all objects have been "cleaned up" call
- System.runFinalization();
- and
This may be really basic and it may also seem to defeat the purpose of automatic garbage collection, but it has helped me with similar problems. Also make sure you delete the JavaSession (LS2J) object.
dgg
Return to top
. . RE: Memory leak on LS agent calling... (~Richard Nontoo... 15.Jan.04) 
Print this page
